Methods, systems, and computer program products for providing quality of service brokering in a network

ABSTRACT

Exemplary embodiments relate to methods, systems, and computer program products for providing quality of service brokering in a network. Methods include receiving a data packet at a router in an Internet protocol (IP) network. The data packet includes a data packet QoS class and a data packet destination. A storage mechanism that includes possible routes to the data packet destination at the data packet QoS class is accessed. One of the possible routes is selected. The data packet is transmitted along the selected route to the data packet destination.

BACKGROUND

Exemplary embodiments relate generally to networks, and moreparticularly, to methods, systems and computer program products forproviding quality of service brokering in a network.

Customers are increasingly asking service providers to manage computerconnections from one geographic location to another and these computerconnections often involve multiple carriers and multiple networks. Whena customer requests a particular bandwidth for a particular quality ofservice (QoS) level, the service providers may have to negotiate withmultiple carriers to provide the requested service. Typically, theservice providers negotiate contracts on a case-by-case basis with eachcarrier and mark the traffic according to the negotiated contract. Theinitial setup of a requested service, including the negotiation androuter set-up, can be a cumbersome and lengthy process. If there are anychanges in the traffic, such as Internet protocol address changes, thenthe negotiated connections are broken and can take time and manualeffort to re-establish.

As more service providers look to add voice and video content to theirbroadband networks, typically through the use of outside contentproviders, the need for a committed QoS level to provide a good customerexperience is increasing. Currently, service providers can only controlthe QoS in their own networks. These providers can negotiate QoScontracts with other providers, but this has proven to be a cumbersomeprocess. It would be desirable to implement an easy to use, standardprocess for negotiating and transmitting QoS information across multiplenetworks.

SUMMARY

Exemplary embodiments relate to methods, systems, and computer programproducts for providing quality of service brokering in a network.Methods include receiving a data packet at a router in an Internetprotocol (IP) network. The data packet includes a data packet QoS classand a data packet destination. A storage mechanism that includespossible routes to the data packet destination at the data packet QoSclass is accessed. One of the possible routes is selected. The datapacket is transmitted along the selected route to the data packetdestination.

Systems for providing quality of service brokering in a network includean input device on a router in an IP network and a processor incommunication with the input device. The input device receives a datapacket. The data packet includes a data packet QoS class and a datapacket destination. The processor includes computer instructions forfacilitating accessing a storage mechanism. The storage mechanism storespossible routes to the data packet destination at the data packet QoSclass. One of the possible routes is selected and the data packet istransmitted along the selected route to the data packet destination.

Computer program products for a scheduler for providing quality ofservice brokering in a network include a storage medium readable by aprocessing circuit and storing instructions for execution by theprocessing circuit for facilitating a method. The method includesreceiving a data packet at a router in an Internet protocol (IP)network. The data packet includes a data packet QoS class and a datapacket destination. A storage mechanism that includes possible routes tothe data packet destination at the data packet QoS class is accessed.One of the possible routes is selected. The data packet is transmittedalong the selected route to the data packet destination.

Other systems, methods, and/or computer program products according toexemplary embodiments will be or become apparent to one with skill inthe art upon review of the following drawings and detailed description.It is intended that all such additional systems, methods, and/orcomputer program products be included within this description, be withinthe scope of the present invention, and be protected by the accompanyingclaims.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings wherein like elements are numbered alikein the several FIGURES:

FIG. 1 is a block diagram of a system for providing quality of servicebrokering in a network that may be implemented by exemplary embodiments;and

FIG. 2 is a flow diagram of an exemplary process for providing qualityof service brokering in a network.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Routers on the Internet already communicate routing path updates via theBorder Gateway Protocol (BGP). This is a well known, standardizedprotocol for performing inter-domain routing in transmission-controlprotocol/Intenet protocol (TCP/IP) networks. BGP is an exterior gatewayprotocol (EGP) that supports routing between multiple autonomous systemor domains and exchanges routing and accessibility information withother BGP systems. Many current routers support the BGP protocol. Partof the BGP standard is the notion of BGP communities. These are groupsof BGP speaking routers or IP addresses that can be treated as one BGPentity by a router for the purposes of applying polices. BGP communitiesare already used to create Multi Protocol Label Switching (MPLS) BGPvirtual private networks (VPNs) per IETF RFC 2547.

Exemplary embodiments create a group of BGP community addresses thatwill map to specific quality of service (QoS) classes in a standardizedway so that these classes have global significance across differentnetworks and different carriers. A data field is added to the BGP headerto indicate that “provider x” has “y amount” of bandwidth available incommunity “abc.” This information is stored (e.g, in a storagemechanism), along with other BGP information, at the BGP routers.

In exemplary embodiments, carriers create a separate MPLS tunnel ontheir networks for each QoS class/BGP community using RSVP so that thebandwidth allocation can be monitored. RSVP provides the mechanism torecord the amount of bandwidth requested. In addition, each carrierpublishes a price list including the classes available and the price perunit of bandwidth. In exemplary embodiments, BGP accounting, alreadyimplemented on most BGP routers, is utilized to provide the trafficsource and usage information for billing purposes.

FIG. 1 is a block diagram of a system for providing QoS brokering in anetwork that may be implemented by exemplary embodiments. A customer mayask a service provider to provide a communication path of a specifiedbandwidth between Atlanta and Los Angeles. In addition, the customer mayspecify a particular QoS level that is required. In exemplaryembodiments, the QoS level (or class) will map to a BGP community (inthis example community “625”). The service provider negotiates withcarrier one 104, carrier two 108 and carrier three 112 to provide thespecified bandwidth at the particular QoS level that is required by thecustomer. As described below with reference to FIG. 2, the negotiationmay be performed manually and/or automatically via a computer. Once thenegotiations and setup are complete, the string “625” is added to theBGP header for all traffic (e.g., data packets) from the customeroriginating from the router 102 in Atlanta and being sent to the router114 in Los Angeles. When the routers along the path (e.g., router 102,router 106, router 110, and router 114) see the string “625” in a BGPheader for a data packet they know what QoS to provide for the datapacket. In exemplary embodiments, the routers are BGP routers and theyinclude an input device for receiving a data packet and a storagemechanism for storing BGP routing information.

FIG. 2 is a flow diagram of an exemplary process for providing QoSbrokering in a network. It could be performed at any of the routersdepicted in FIG. 1. At block 202, it is determined if a router hasreceived a data packet. If the router has received a data packet, thenblock 204 is performed to access a storage mechanism that includespossible routes between the router and a data packet destination (e.g, arouter and a switch) specified in the data packet. Also specified by thedata packet (e.g., in the header) is a QoS for the data packet (e.g,specified as a BGP community address). At block 206, one of the possibleroutes for the data packet is selected from the possible routescontained in the storage mechanism. At block 208, the data packet istransmitted along the selected route to the data packet destination atthe specified QOS.

In exemplary embodiments, the data packet also includes a data packetcustomer identifier which may be utilized to select one of the possibleroutes. (e.g., only select a route that has bandwidth that has beenreserved for the customer). Alternatively, or in addition, the customeridentifier may be utilized to perform accounting functions such asbilling the customer for the bandwidth utilized when transmitting thedata packet. In exemplary embodiments, the router keeps track of thebandwidth utilized by recording the customer identifier along with thebandwidth and QoS that was used by the data packet. The billinginformation may be stored at the router and periodically transmitted toa billing system, or it may be stored outside of the router. The BGPaccounting records may be utilized to initiate the customer billing.Alternate embodiments include the routers specifying the availablebandwidth (if any) for each of the possible routes at the QoS specifiedby the data packet. Selecting a route is responsive to there beingavailable bandwidth at the specified QoS. In this manner, a carrier maysell excess or currently unused bandwidth on a first come first servebasis and as a result may have increased utilization. In addition, ifbandwidth on the QoS specified isn't available, but bandwidth on ahigher level QoS is available, the data packet may be routed via thehigher QoS level (in some cases at the same price as the requested QoS).

The data packet may be received via a first carrier and transmitted viaa second carrier. By utilizing an additional field in the BGP header,the QoS class associated with the data packet may be universally knownby multiple carriers across multiple networks. For example, referring toFIG. 1, a service provider may have negotiated contracts, includingbandwidth and QoS requirements with carrier one 104, carrier two 108 andcarrier three 112. When a data packet is received at an input device onrouter 102, it includes a BGP community in the heading (e.g., “625)which indicates the required QoS to be associated with the data packet.When router 102 receives the data packet it knows, based on the BGPcommunity (e.g., by looking up the QoS that corresponds to the BGPcommunity in a storage mechanism on the router), which QoS to apply tothe data packet.

Similarly, when the data packet is received at an input device on router106, the router 106 knows which QoS to apply to the data packet based onthe BGP community of “625” in the heading and the common definition ofwhat QoS should be applied to community “625.” Router 102 and router 106may be in different networks (including IP networks) and be managed bydifferent carriers. The common definition of the QoS indicated by a BGPcommunity of “625” allows the routers to quickly determine the correctQoS for each of the data packets for inter-carrier and inter-networkdata packets.

Referring to FIG. 2, if it is determined at block 202 that the routerhas not received a data packet, then block 210 is performed. At block210, it is determined if a request to reserve bandwidth has beenreceived at the router. If a request to reserve bandwidth has beenreceived at the router, then block 212 is performed. The request is froma customer (e.g., a service provider acting on behalf of a end customer,and an end customer) and includes a requested destination and arequested QoS class (e.g, specified as a BGP community). At block 212, acheck is made (e.g., by accessing the storage mechanism on the router ora storage mechanism in some other location) to verify that the requestedbandwidth is available at the requested QoS class. At block 214, therequested bandwidth at the requested QoS class is reserved, it if isavailable as determined at block 212. The reservation of the bandwidthis recorded in the storage mechanism.

The processing described in reference to blocks 210 through 214 may beperformed manually and/or in an automated fashion for each of therouters depicted in FIG. 1. In response to the request from the customerfor a specified bandwidth at a particular QoS level, the serviceprovider will ask each carrier along the route if they have the requiredbandwidth at the requested QoS. Referring to FIG. 1, the serviceprovider may request, from carrier one 104, 25 megabytes (MBs) ofbandwidth in a “625” community class between router 102 and router 106.This inquiry about availability may be handled at the router 102 basedon information stored in the storage mechanism or elsewhere.Alternatively, carrier one 104 and other carriers may publish availablebandwidth and QoS so that a service provider can determine networkavailability.

Once it is determined that the requested bandwidth, at the requested QoSis available between router 102 and router 106, the requested bandwidthat the requested QoS is reserved. In exemplary embodiments, thereservation is performed by updating the storage mechanism on the routerto reflect the reservation. In embodiments where a list of availablebandwidth and QoS is published by the carriers, the list would beupdated as a result of the reservation.

Referring to FIG. 1, the service provider may then request, from carriertwo 108, 25 megabytes (MBs) of bandwidth in a “625” community classbetween router 106 and router 110. This inquiry about availability maybe handled at the router 106 based on information stored in the storagemechanism or elsewhere. Alternatively, carrier two 108 and othercarriers may publish available bandwidth and QoS so that a serviceprovider can determine network availability. The reservation processcontinues until the service provider has reserved the bandwidth requiredat the QoS required for the customer. As used herein, the terms serviceprovider and customer may be used interchangeably. A service providermay be considered to be the customer for the carriers, and the serviceprovider may be reserving the bandwidth for a customer of the serviceprovider. In addition, a customer may be reserving the bandwidth for itsown use and may or may not be considered a service provider.

In the example depicted herein, the same amount of bandwidth and thesame community class are reserved from the Atlanta router 102 to the LosAngeles router 114. In exemplary embodiments, the amount of bandwidthand the BGP community classes may differ between routers for the samecustomer. For example, a bandwidth of 25 MBs in a “625” community classmay be reserved on carrier one 104 between router 102 and router 106,and a bandwidth of 50 MBs in a “999” community class may be reserved oncarrier two 108 between router 106 and 110. The differences may be dueto a variety of factors including bandwidth availability and routercapability.

In other exemplary embodiments, the service provider (or customer) maybe required to authorize the reservation of the bandwidth before thereservation occurs. This may be performed by transmitting a fee for eachof the possible route(s) that fit the bandwidth and QoS requirements andasking the service provider (or customer) to select the route thatshould be reserved. In response to receiving an authorization from theservice provider (or customer), the bandwidth is reserved.

If it has been determined at block 210, that a request to reservebandwidth has not been received at the router, then block 216 isperformed. At block 216 it is determined if a request to update thestorage mechanism on the router has been received. If a request toupdate the storage mechanism on the router has been received, then block218 is performed and the storage mechanism is updated to reflect therequested update. Updates may include, adding a new route, deleting anexisting route and updating an existing route (e.g., adding morebandwidth and adding a different QoS). In exemplary embodiments, theupdate information is received at the router via a BGP community addressthat specifies a QoS class.

Exemplary embodiments may be utilized to implement an easy to use andstandard process for negotiating and transmitting quality of serviceinformation across multiple networks and/or multiple carriers. Inaddition, exemplary embodiments may be utilized to transmit data packetsacross multiple networks and/or multiple carriers in an efficientmanner.

As described above, embodiments may be in the form ofcomputer-implemented processes and apparatuses for practicing thoseprocesses. In exemplary embodiments, the invention is embodied incomputer program code executed by one or more network elements.Embodiments include computer program code containing instructionsembodied in tangible media, such as floppy diskettes, CD-ROMs, harddrives, or any other computer-readable storage medium, wherein, when thecomputer program code is loaded into and executed by a computer, thecomputer becomes an apparatus for practicing the invention. Embodimentsinclude computer program code, for example, whether stored in a storagemedium, loaded into and/or executed by a computer, or transmitted oversome transmission medium, such as over electrical wiring or cabling,through fiber optics, or via electromagnetic radiation, wherein, whenthe computer program code is loaded into and executed by a computer, thecomputer becomes an apparatus for practicing the invention. Whenimplemented on a general-purpose microprocessor, the computer programcode segments configure the microprocessor to create specific logiccircuits.

While the invention has been described with reference to exemplaryembodiments, it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted forelements thereof without departing from the scope of the invention. Inaddition, many modifications may be made to adapt a particular situationor material to the teachings of the invention without departing from theessential scope thereof. Therefore, it is intended that the inventionnot be limited to the particular embodiments disclosed for carrying outthis invention, but that the invention will include all embodimentsfalling within the scope of the claims.

1. A method for providing quality of service (QoS) brokering in anetwork, the method comprising: receiving a data packet at a router inan Internet protocol (IP) network, the data packet including a datapacket QoS class and a data packet destination; accessing a storagemechanism by a processor that includes possible routes to the datapacket destination at the data packet QoS class; selecting one of thepossible routes; and transmitting the data packet along the selectedroute to the data packet destination wherein: the receiving is from afirst carrier and the transmitting is via a second carrier.
 2. Themethod of claim 1 wherein the data packet QoS class is specified as aBorder Gateway Protocol (BGP) community address that corresponds to thedata packet QoS class.
 3. The method of claim 1 wherein the data packetfurther includes a data packet customer identifier, and the methodfurther comprises initiating a customer bill for the transmitting,wherein the customer bill specifies the data packet customer identifier.4. The method of claim 3 wherein the initiating a customer bill utilizesBGP accounting records.
 5. The method of claim 3 wherein the billcontains information that is stored at the router and transmitted to abilling system on a predetermined interval.
 6. The method of claim 1wherein the receiving is from a second IP network.
 7. The method ofclaim 1 further comprising accessing the storage mechanism to verifythat the data packet is from a customer who has reserved bandwidth atthe data packet QoS class to the data packet destination.
 8. The methodof claim 1 wherein the storage mechanism further includes availablebandwidth for each of the possible routes at the data packet QoS class,and the selecting includes verifying that the selected route has enoughbandwidth at the data packet QoS class for processing the data packet.9. The method of claim 1 further comprising: receiving a request toreserve a requested bandwidth from a customer, the request including arequested destination and a requested QoS class; verifying that therequested bandwidth at the requested QoS class is available between therouter and the requested destination; and reserving the requestedbandwidth at the requested QoS class between the router and therequested destination for the customer, the reserving including updatingthe storage mechanism to reflect the customer, the requested QoS classand the requested destination, wherein the reserving is performed inresponse to the requested bandwidth at the requested QoS class beingavailable between the router and the requested destination.
 10. Themethod of claim 9 further comprising: p1 transmitting a request forauthorization from the customer to reserve the requested bandwidth, therequest for authorization including a fee for each of the possibleroutes from the router to the requested destination at the requestedclass of service; receiving the authorization; and performing thereserving in response to receiving the authorization.
 11. The method ofclaim 1 further comprising: receiving a requested update to the storagemechanism including one or more of a new possible route, a deletion ofone of the possible routes and an update to one of the possible routes;and updating the storage mechanism to reflect the requested update. 12.The method of claim 11 wherein the update is received via a BGP headerrecord which includes a community address that specifies an updated QoSclass.
 13. The method of claim 1 wherein the destination includes atleast one of a router and a switch.
 14. A system for providing qualityof service brokering, the system comprising: an input device on a routerin an IP network for receiving a data packet from a first carrier, thedata packet including a data packet QoS class and a data packetdestination; and a processor including computer instructions forfacilitating: accessing a storage mechanism, the storage mechanismstoring possible routes to the data packet destination at the datapacket QoS class; selecting one of the possible routes; and transmittingthe data packet via a second carrier along the selected route to thedata packet destination.
 15. The system of claim 14 wherein the routeris BGP enabled and the data packet QoS class is specified as a BGPcommunity address that corresponds to the data packet QoS class.
 16. Thesystem of claim 14 wherein the processor includes further instructionsto facilitate: receiving a requested update to the storage mechanismincluding one or more of a new possible route, a deletion of one of thepossible routes and an update to one of the possible routes, wherein therequested update is received via a BGP header record which includes acommunity address that specifies an updated QoS class; and updating thestorage mechanism to reflect the requested update.
 17. The system ofclaim 14 wherein the processor includes further instructions tofacilitate: receiving a request to reserve a requested bandwidth amountfrom a customer, the request including a requested destination and arequested QoS class; verifying that the requested bandwidth at therequested QoS class is available between the router and the requesteddestination; and reserving the requested bandwidth at the requested QoSclass between the router and the requested destination for the customer,the reserving including updating the storage mechanism to reflect thecustomer, the requested QoS class and the requested destination, whereinthe reserving is performed in response to the requested bandwidth at therequested QoS class being available between the router and the requesteddestination.
 18. A computer program product for providing quality ofservice brokering in a network, the computer program product comprising:a storage medium readable by a processing circuit and storinginstructions for execution by the processing circuit for facilitating amethod comprising: receiving a data packet from a first carrier at arouter in an Internet protocol (IP) network, the data packet including adata packet QoS class and a data packet destination; accessing a storagemechanism that includes possible routes to the data packet destinationat the data packet QoS class; selecting one of the possible routes; andtransmitting the data packet via a second carrier along the selectedroute to the data packet destination.
 19. The computer program productof claim 18 wherein the method further comprises: receiving a request toreserve a requested bandwidth amount from a customer, the requestincluding a requested destination and a requested QoS class; verifyingthat the requested bandwidth at the requested QoS class is availablebetween the router and the requested destination; and reserving therequested bandwidth at the requested QoS class between the router andthe requested destination for the customer, the reserving includingupdating the storage mechanism to reflect the customer, the requestedQoS class and the requested destination, wherein the reserving isperformed in response to the requested bandwidth at the requested QoSclass being available between the router and the requested destination.20. The computer program product of claim 18 wherein the router is BGPenabled and the data packet QoS class is specified as a BGP communityaddress that corresponds to the data packet QoS class.